Method and apparatus of managing stored system information using validly timer when applying discontinuous reception mode in mobile communication system

ABSTRACT

A method for managing system information using a valid period timer includes receiving system information from a base station, checking whether information related to the management of a valid timer time regarding system information is included in the system information, and determining the valid timer time regarding the system information according to the checking result, and starting a timer by employing the determined valid timer time and managing the system in formation. A terminal a controller configured to control the transceiver to receive system information from a base station, check whether information related to management of a valid timer time regarding system information is included in the system information, determine the valid timer time regarding the system information according to the checking result, start a timer set for the determined valid timer time, and manage the system information.

CROSS-REFERENCE TO RELATED APPLICATION AND CLAIM OF PRIORITY

The present application is related to and claims the priority under 35U.S.C. § 119(a) to U.S. Application Ser. No. 62/204,315 filed in theU.S. Patent and Trademark Office on Aug. 12, 2015, the entire content ofwhich is hereby incorporated by reference.

TECHNICAL FIELD

The present disclosure relates to a method of managing systeminformation in discontinuous reception mode in a mobile communicationsystem, and more particularly to a method of managing system informationusing a valid period timer.

BACKGROUND

In order to meet the increase in the demand for wireless data trafficafter the commercialization of 4G communication systems, considerableeffort has been made to develop pre-5G communication systems or improved5G communication systems. This is one reason why ‘5G communicationsystems’ or ‘pre-5G communication systems’ are called ‘beyond 4G networkcommunication systems’ or ‘post LTE systems.’ In order to achieve a highdata transmission rate, 5G communication systems are being developed tobe implemented in a band of extremely high frequency, or millimeter wave(mmWave), e.g., a band of 60 GHz. In order to reduce the occurrence ofstray electric waves in a band of extremely high frequency energy and toincrease the transmission distance of electric waves in 5G communicationsystems, various technologies being explored, for example: beamforming,massive MIMO, Full Dimensional MIMO (FD-MIMO), array antennas, analogbeam-forming, large scale antennas, etc. In order to improve systemnetworks for 5G communication systems, various technologies have beendeveloped, e.g., evolved small cell, advanced small cell, cloud radioaccess network (cloud RAN), ultra-dense network, Device-to-Devicecommunication (D2D), wireless backhaul, moving network, cooperativecommunication, Coordinated Multi-Points (CoMP), interferencecancellation, etc. In addition, for 5G communication systems, othertechnologies have been developed, e.g., Hybrid FSK and QAM Modulation(FQAM) and Sliding Window Superposition Coding (SWSC), as AdvancedCoding Modulation (ACM), Filter Bank Multi Carrier (FBMC),non-orthogonal multiple access (NOMA), sparse code multiple access(SCMA), etc.

The Internet has evolved from a human-based connection network, wherehumans create and consume information to the Internet of Things (IoT)where distributed configurations, such as objects, exchange informationwith each other to process the information. The technology related tothe IoT is starting to be combined with, for example, technology forprocessing big data through connection with a cloud server, and this iscalled an Internet of Everything (IoE) technology. In order to manifestthe IoT, various technical components are required, such as, a sensingtechnology, wired/wireless communication and network infra technology, aservice interfacing technology, a security technology, etc. In recentyears, a sensor network for connecting objects, Machine to Machine(M2M), Machine Type Communication (MTC), etc. have been researched. Inthe IoT environment, intelligent Internet Technology (IT) services maybe provided to collect and analyze data acquired from objects connectedto each other and thus a create new value for human life. As existinginformation technologies are fused and combined with various industries,the IoT may also be applied within various fields, such as: smart homes,smart buildings, smart cities, smart cars or connected cars, smartgrids, health care, smart home appliances, high quality medicalservices, etc.

Various attempts have been made to apply 5G communication systems to theIoT network. For example, various technologies related to sensornetworks, Machine to Machine (M2M), Machine Type Communication (MTC),etc., have been implemented by beam-forming, MIMO, array antenna, etc.,as 5G communication technology. The application of the cloud RAN as abig data processing technology described above may be an example of ahybrid of 5G technology and IoT technology.

As such, in order to satisfy the demand for wireless data traffic,people in various fields are discussing the development of communicationmethods, e.g., device-to-device communication (D2D), a frequencyaggregation system for a number of cells, a multiple antenna systemusing large scale antennas, etc.

SUMMARY

To address the above-discussed deficiencies, it is a primary object toprovide a method and apparatus for managing system information, using avalid period timer, in discontinuous reception mode, in a mobilecommunication system.

In accordance with an aspect of the present disclosure, a method for aterminal to manage system information in a mobile communication systemis provided. The method includes: receiving system information from abase station; checking whether information related to the management ofa valid time regarding system information is included in the systeminformation, and determining a valid time regarding the systeminformation according to the checking result; and starting a timer byemploying the determined valid time (validity timer) and managing thesystem information.

In accordance with another aspect of the present disclosure, a methodfor a base station to transmit system information in a mobilecommunication system is provided. The method includes: determiningwhether the base station includes information related to the managementof a valid time regarding system information in the system information,in order to determine the valid time; and transmitting the systeminformation to a terminal so that the terminal starts a timer byemploying the valid time (validity timer) determined according to thedetermination as to whether information related to the management of avalid time is included in the system information.

In accordance with another aspect of the present disclosure, a terminalconfigured to manage system information in a mobile communication systemis provided. The terminal includes: a transceiver for performing thetransmission/reception of signals; and a controller for: controlling thereception of system information from a base station; checking whetherinformation related to the management of a valid time regarding systeminformation is included in the system information; determining a validtime regarding the system information according to the checking result;starting a timer by employing the determined valid time (validitytimer); and managing the system information.

In accordance with another aspect of the present disclosure, a basestation configured to transmit system information in a mobilecommunication system is provided. The base station includes: atransceiver for performing the transmission/reception of signals; and acontroller: determining whether the base station includes informationrelated to the management of a valid time regarding system informationin the system information, in order to determine the valid time; andtransmitting the system information to a terminal so that the terminalstarts a timer by employing the valid time (validity timer) determinedaccording to the determination as to whether information related to themanagement of a valid time is included in the system information.

Before undertaking the DETAILED DESCRIPTION below, it may beadvantageous to set forth definitions of certain words and phrases usedthroughout this patent document: the terms “include” and “comprise,” aswell as derivatives thereof, mean inclusion without limitation; the term“or,” is inclusive, meaning and/or; the phrases “associated with” and“associated therewith,” as well as derivatives thereof, may mean toinclude, be included within, interconnect with, contain, be containedwithin, connect to or with, couple to or with, be communicable with,cooperate with, interleave, juxtapose, be proximate to, be bound to orwith, have, have a property of, or the like; and the term “controller”means any device, system or part thereof that controls at least oneoperation, such a device may be implemented in hardware, firmware orsoftware, or some combination of at least two of the same. It should benoted that the functionality associated with any particular controllermay be centralized or distributed, whether locally or remotely.Definitions for certain words and phrases are provided throughout thispatent document, those of ordinary skill in the art should understandthat in many, if not most instances, such definitions apply to prior, aswell as future uses of such defined words and phrases.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure and itsadvantages, reference is now made to the following description taken inconjunction with the accompanying drawings, in which like referencenumerals represent like parts:

FIG. 1 is a diagram that describes a communication scenario inmachine-type communication (MTC);

FIG. 2 is a diagram that describes the concept of a paging time point inthe long term evolution (LTE) technology;

FIG. 3 is a diagram that describes the concept of a time point whenpaging occurs according to the present disclosure;

FIG. 4 is a diagram that describes a method of altering systeminformation in the LTE technology;

FIG. 5 is a diagram that describes a method of notifying user equipment(UE) of altered system information using SIB1 according to the presentdisclosure;

FIG. 6 is a flowchart that describes that describes a method for userequipment (UE) to check altered system information using SIB1 accordingto the present disclosure;

FIG. 7 is a flowchart that describes that describes a method for eNB tonotify altered system information using SIB1 according to the presentdisclosure; and

FIG. 8 is a flowchart that describes a method for UE to manage storedsystem information using system information and a valid period timeraccording to the present disclosure.

DETAILED DESCRIPTION

FIGS. 1 through 8, discussed below, and the various embodiments used todescribe the principles of the present disclosure in this patentdocument are by way of illustration only and should not be construed inany way to limit the scope of the disclosure. Those skilled in the artwill understand that the principles of the present disclosure may beimplemented in any suitably arranged telecommunication technologies.

Embodiments of the present disclosure are described in detail referringto the accompanying drawings. Detailed descriptions of well-knownfunctions and structures incorporated herein may be omitted to avoidobscuring the subject matter of the disclosure. The terms or wordsdescribed in this description and the claims should not be limited by ageneral or lexical meaning, instead should be analyzed as a meaning anda concept through which the inventor defines and describes thedisclosure to the best of his/her ability, to comply with the idea ofthe disclosure.

Although the following embodiments are described based on Long TermEvolution (LTE) systems and LET-Advanced (LTE-A) systems, it will beappreciated to those skilled in the art that the subject matter of thepresent disclosure can also be applied to various types of communicationsystems using discontinuous reception (DRX) mode.

FIG. 1 is a diagram that describes a communication scenario inmachine-type communication (MTC).

Machine-type communication (MTC) devices 105 are connected to a wirelessservice provider network 110. MTC devices 105 can refer to variousunmanned/automated machines, such as meters, vending machines, etc. MTCdevices 105 have features that differ from existing wireless terminalsin terms of various aspects. The features of MTC devices can varyaccording to the types. A number of MTC devices with various featurescan exist in one cell.

The MTC server 115 has information regarding MTC devices 105 andperforms authentication. The MTC server 115 collects information fromthe MTC devices 105, and transmits the collected information to the MTCuser 120. The MTC server 115 can be inside or outside the wirelessservice provider network. The MTC user 120 refers to an end user thatneeds information that the MTC devices transmitted.

Machine-type communication (MTC) has features that differ from those ofexisting wireless communication. The features of MTC are classified intovarious categories according to use purpose. For example, when MTCdevices need communication only a few times a day regardless of time,they are ‘Time Tolerant.’ When MTC devices are installed at a site andperform the collection and transmission of specified information, theyare ‘low mobility.’ Wireless service providers need to provide services,considering various types of features of MTC and the coexistence withexisting terminals.

In particular, MTC devices, related to the tracking of animals, freightvehicles, etc., are equipped with a battery or a self-powered system.Since these types of MTC devices must use limited power, it ispreferable that they need to be designed to consume an extremely smallamount of power, efficiently. WG SA1 in the 3GPP has defined an extralow power consumption mode where MTC devices can be set to consume lowpower.

Increasing a discontinuous reception (DRX) cycle is one of the methodsof reducing power consumption. User equipment (UE) performs thereception to receive a paging signal from an eNB. Paging signals are notsignals frequently transmitted from eNBs. When UE performs the receptionto receive a paging signal during a period time when it does not arrive,it causes power consumption.

In order to reduce power consumption, UE is capable of performing thereception operation and making an attempt to receive a paging signal foronly a specified time interval periodically, and this is calleddiscontinuous reception (DRX). In LTE system, UE devices in an idlestate perform the DRX operation describe as in the following Equation 1.The system frame number (SFN) per radio frame increases by one. When apaging signal is transmitted via a radio frame satisfying the equation,UE performs the reception operation based on DRX. The radio frame iscalled Paging Frame (PF).SFN mod T=(T div N)*(UE_ID mod N)  [Equation 1]

-   -   where    -   SFN: System Frame Number. 10 bits (MSB 8 bits explicit, LBS 2        bits implicit)    -   T: DRX cycle of the UE. Transmitted on SIB2. ENUMERATED {rf32,        rf64, rf128, rf256}    -   N: min (T, nB)    -   nB: Transmitted on SIB2. ENUMERATED {4T, 2T, T, T/2, T/4, T/8,        T/16, T/32}    -   UE_ID: IMSI mod 1024 (IMSI is a unique number assigned to UE)    -   8 bits of Master Information Block (MIB) of Physical Broadcast        Channel (PBCH) represent SFN. T and nB refer to values that are        contained in System Information Block Type2 (SIB2) provided by        an eNB. T can be one of the values, rf32, rf64, rf128, and        rf256. For example, r32 refers to the length of a 32 radio        frame. That is, r32 is 320 ms.

FIG. 2 illustrates the example concept of a paging time point in thelong term evolution (LTE) technology.

The SFN increases by one every radio frame, as indicated by referencenumber 205. The SFN has a cycle of 1024, and is set to ‘0,’ as indicatedby reference number 210. Based on Equation 1, a paging message of thesame pattern repeats every SFN cycle as indicated by reference number215. From Equation 1, the maximum DRX cycle in the current LTE standardis 2.56 seconds. Although the DRX cycle increases to the maximum, itcannot exceed the SFN cycle, i.e., 10.24 seconds. That is, in order toreduce power consumption, the DRX cycle increases to greater than orequal to 10.24 seconds and simultaneously the SFN cycle also needs toincrease. In order to increase the SFN cycle, the present disclosureincludes additional SFN bits in an existing or new system informationblock (SIB) and defines the operations of UE receiving the SIB. Thenumber of SFN bits increases by one every SFN cycle. The SIB includingSFN bits does not need to be received by all UE devices. Only UE using arelatively long DRX cycle attempts to perform the reception operation.

systemInfoValueTag value (one IE included in SIB1), which increases byone each time that SIB information is altered, andsystemInfoModification IE, which is included in pages and indicates acondition as to whether SI has been altered, are not affected from thechange in the value of SFN bits. That is, although the value of SFN bitsis altered, the systemInfoValueTag IE is not updated and thesystemInfoModification IE is not transmitted via a paging operation.

In the embodiment, in order to extend the DRX cycle and simultaneouslyincrease the success probability of receiving paging signals, it isassumed that attempts to receive a paging signal are performed a numberof times for a preset DRX interval. To this end, a paging time point isdetermined by the following two steps.

1) Step 1: determine an SFN cycle during which a paging for an MTCdevice will occur.

2) Step 2: determine a radio frame that will occur during the SFN cycledetermined at step 1.

At step 1, an SFN cycle during which a paging will occur is determined.The value of added SFN bits increases by one every one SFN cycle. Thevalue of added SFB bits is defined as Hyper SFN (HFN). SFN cycles duringwhich a paging will occur are acquired by the following Equation 2. Inthe present disclosure, a corresponding SFN cycle is called a PagingHyper Frame (PHF).HFN mod T′=(T div N′)*(UE_ID mod N′)  [Equation 2]

where

-   -   N′: min (T′, nB′)    -   UE_ID: IMSI mod 1024 (or MTC device group ID mod 1024)

Where T′ and nB′ refers to values provided by an eNB. T′ and nB′ can beincluded in SIB 2, along with existing T and nB. UE_ID can be derivedthrough an IMSI module operation the same as general UE. Since MTCdevices can be represented as devices of a group ID form, they can alsoemploy a group ID. After determining SFN cycles during which a page willoccur, a radio frame where a paging will occur during a correspondingSFN cycle is determined at step 2. The determination of a radio framecan be implemented with Equation 1.

When a time point when a paging will occur is defined via the two stepsdescribed above and thus MTC devices have a corresponding DRX cycle,power consumption can be greatly reduced. In addition, since the pagingaccording to the setup of T and nB can repeat during the SFN cycledetermined at step 1, the probability of receiving a paging canincrease, which is advantageous.

FIG. 3 illustrates an example concept of a time point when paging occursaccording to the present disclosure.

An HFN increases by one every SFN cycle, indicated by reference number305. An SFN cycle during which a paging will occur, indicated byreference number 310, is determined according to Equation 2. An SFNincreases by one every radio frame, indicated by reference number 315.An eNB is capable of creating a paging via Equation 3 during the SFNcycle determined via Equation 2, as indicated by reference number 320.

FIG. 4 illustrates an example operation of altering system informationin the LTE technology.

The system information broadcast by an eNB is altered based on amodification period (MP). An eNB is capable of broadcasting newlyaltered system information, except for part of the system information,from a time point that every modification period starts.

An eNB is capable of notifying UE devices, in a modification period(previous modification period) before broadcasting newly altered systeminformation, that it will broadcast the newly altered system informationfrom the next modification period. For example, when an eNB broadcastssystem information from the n+1th modification period 405, it notifiesUE devices in the nth modification period that system information hasbeen altered. To this end, the eNB uses a paging message to notify UE ofthe alternation of system information, and UE needs to receive a pagingmessage at least once during the modification period.

When systemInfoModification IE is included in a paging message, thismeans that newly updated system information is transmitted from the nextmodifications period following the modification period during which thepaging message has been transmitted. When system information, except forpart of the system information, is altered, systemInfoValueTag valueincluded in SIB1 also increases by one. UE, camped on again from theout-of coverage, can use the paging message to determine whether itsstored system information is identical to system information that iscurrently broadcast from an eNB.

UE can be implemented in such a way as to determine whether systeminformation is altered, using systemInfoValueTag of an SIB1 or a pagingmessage. When a DRX cycle is extended to be greater than the maximum ofa modification period in order to reduce power consumption, UE may notreceive a paging during the period. In this case, UE cannot determinewhether system information is updated. In order to resolve the problem,a solution is needed.

The present disclosure provides a method capable of determining whethersystem information is updated when a DRX cycle is extended to be greaterthan the maximum of a modification period in order to reduce powerconsumption. When system information (SI) is updated, the SI updateneeds to be notified to all UE devices in an idle mode. The notificationof SI update is performed via a paging message. Since an eNB does notknow whether UE in an idle mode exists within the coverage area, ittransmits paging message via all available PO, during the modificationperiod.

In LTE standard, a modification period is an integer multiple of adefault DRX cycle. On the other hand, the Extended DRX (eDRX) has alength of a DRX cycle, reaching tens of minutes. In order to notify UEusing the eDRX of a condition as to whether system information isupdated, the continuous transmission of a paging message can beperformed over the overall duration of a DRX cycle. However, thisoperation leads to an excessive waste of radio resources.

An existing system information (SI) updating method applied to generalDRX UE is the pre-notification. Therefore, when the DRX UE detects thepresence of SI update, it performs the SI refresh in the nextmodification period (MP). The present disclosure checks a SIB1 for eDRXUE, in part of the HF after the time point that SI update occurs, anddetermines whether the SI is updated. That is, the existing SI updatingmethod applied to eDRX UE is the post-notification. Therefore, when theeDRX UE detects the presence of SI update, it needs to perform the SIrefresh.

When SI is updated during the MP [m+1], the eNB transmits a pagingmessage for legacy DRX UE via all available PS of all available PFduring the MP [m]. However, the eNB does not transmit an additionalpaging message for the eDRX UE. Instead, the eDRX UE acquires MIB andSIB1 at every PHF, and detects systemInfoValueTag information in theSIB 1. A precise time point can be acquired by the following plans.

-   -   Plan 1: acquire SIB1 and the first MIB of PHF    -   Plan 2: acquire SIB1 and MIB closest to the first PF/PO of PHF

FIG. 5 illustrates an example operation of notifying user equipment (UE)of altered system information using SIB1 according to the presentdisclosure.

UE employing the eDRX monitors a paging in only the PHF, based on aHyper SFN, as indicated by reference number 500. In the PHF, UE canreceive a paging from the PF/PO derived by applying existing oradditional DRX parameters. SI update, indicated by reference number 505,can occur in a time interval 525, not in the PHF. When SI updated fromand after the m+1^(th) MP 520 is broadcast according to a legacyprocedure, an eNB notifies UE devices of the SI update, at the m^(th) MP515, using a paging, as indicated by reference number 510.

Since UE employing the eDRX is not PHF during a corresponding period oftime, it does not receive a paging and does not determine whether SI isupdated. To resolve this problem, the eNB sequentially receives SIB1 andMIB, in the PHF 500, after the SI is updated, and determines whethersystemInfoValueTag value included in the SIB1 is identical to thesystemInfoValueTag value stored in the UE, as indicated by referencenumber 530.

When the systemInfoValueTag value included in the newly received SIB1 isnot identical to the systemInfoValueTag value stored in the UE, UEconsiders that SI update occurred in an interval not the PHF and updatessystem information as currently broadcast system information. ThesystemInfoValueTag can be re-used by eDRX UE. New systemInfoValueTagExtfor additional eDRX UE can be defined.

The systemInfoValueTag has a value of INTEGER, 0, . . . , 31. That is,the systemInfoValueTag has a value from 0 to 31 and increases by oneeach time SI is updated. When the value exceeds 31, thesystemInfoValueTag returns to 0. The systemInfoValueTagExt has a valueof INTEGER, 0, . . . , 256. This is designed because eDRX can have arelatively long duration of a DRX cycle during which SI can be updated anumber of times. The systemInfoValueTagExt may also increase by one eachtime SI is updated. Another plan is that: when the value is wrappedaround, with the re-uses of the systemInfoValueTag value, thesystemInfoValueTagExt value increases by one. This plan may set thesystemInfoValueTagExt value to have a relatively lower range of integervalue, e.g., INTEGER, 0, . . . , 15, and the like, than the previousplan has set. When SI update occurs during the PHF, an indicatornotifying the SI update occurrence is included in a paging message foreDRX UE and new system information can be updated from and after thenext MP in the same as an legacy method.

FIG. 6 is a flowchart that describes a method for user equipment (UE) tocheck altered system information using SIB1 according to the presentdisclosure.

UE is powered on or changes the Tracking Area (TA) in operation 600. TheUE acquires system information from an eNB in operation 605. The UEdetermines whether the system information includes a default eDRX cycleand an nB′ value in operation 610.

When the UE ascertains that the system information includes a defaulteDRX cycle and an nB′ value in operation 610, it performs RRC ConnectionEstablishment in operation 615. When the UE prefers to apply the eDRX,it sends, to an MME, ATTACH REQUEST or TAU REQUEST message including aUE specific DRX cycle and a UE specific eDRX cycle in operation 620.

The UE receives a message, ATTACH ACCEPT or TAU ACCEPT, from the MME inoperation 625. The UE determines whether the message includes an AllowedeDRX parameter in operation 630. The Allowed eDRX parameter can includean indication or a condition as to whether the MME supports the eDRX andinformation regarding an eDRX cycle that the UE needs to employ.

The UE performs a process, RRC Connection Release, in operation 635. TheUE applies eDRX in operation 640. To this end, the UE derives T′ and Tand calculates PHF and PF, using the equations described above inoperation 645. The operation can be performed before performing the RRCConnection Release. When the calculated PHF arrives, the UE sequentiallyreceives MIB and SIB1 in operation 650. The UE checks systemInfoValueTagor systemInfoValueTagExt value in the SIB1 in operation 655. The eDRX UEreceives an SIB1 at least once every T′, i.e., an eDRX cycle, and checkssystemInfoValueTag or systemInfoValueTagExt in the received SIB1.

When the UE performs the DRX operation at an eDRX cycle, it can receiveSIB1 closest, in the domain closest, to the first PF/PO of the PHFdetermined according to the eDRX cycle. Alternatively, the UE canreceive SIB1 closest to the first PF/PO of the PHF, from among SIB iscreated later (or earlier) than the first PF/PO of the PHF.

The UE determines whether its storing value differs from values of theIEs in operation 660. When the UE ascertains that its storing value doesnot differ from values of the IEs in operation 660, it does not need toupdate system information. On the other hand, when the UE ascertainsthat its storing value differs from values of the IEs in operation 660,it receives system information that an eNB is currently broadcasting inoperation 665.

Meanwhile, when the eNB does not broadcast a default eDRX and nB′ inoperation 610 or the MME does not send an Allowed eDRX parameter inoperation 630, the UE performs only a legacy DRX operation in operation670.

Although the embodiment referring to FIG. 6 describes UE in an idlemode, it should be understood that the present disclosure can also beapplied to UE in a connection state (mode). UE in a connection state(mode) can perform the DRX, and also set to operate in a long DRX cycleand a short DRX cycle. The UE applies a short DRX cycle during thetransmission/reception of data and a long DRX cycle while not performingthe transmission/reception of data.

A long DRX cycle can be set to 10 ms-10.24 sec and greater than amodification period. UE in a connection state is capable of checkingSIB1 as described below.

UE establishes RRC connection with an eNB. UE reports a condition as towhether it supports eDRX to the eNB. The eNB can set a relatively longDRX cycle, e.g., 10.24 seconds, for UE capable of supporting eDRX. TheUE performs a first or second operation based on the set length of DRXcycle.

When the set length of long DRX cycle is a first value, the UE performsa first operation. When the set length of long DRX cycle is greater thanor equal to the first value, the UE performs a second operation. Thefirst value can be a fixed value, e.g., 2.56 seconds. Alternatively, thefirst value can be specific values set according to cells, e.g., alength of modification period.

The first operation is as follows. UE checks SIB1 at least once everymodification period and determines whether SI is altered. UE can checkthe first SIB1 of the modification period and determine whether SI isaltered. When UE ascertains that SI is altered, i.e., when UE ascertainsthat a value tag differs from the value stored therein, it receives SIBsagain and replaces its currently stored values with the received SIBs.

The second operation is as follows. UE checks SIB1 at least once duringevery period which has a larger value than the other out of amodification period and a long DRX cycle, and determines whether SI isaltered. For example, when UE determines to check SIB1 at a Long DRXcycle, it can check SIB closest, in time, to onDuration. When UEascertains that SI is altered, i.e., when UE ascertains that a value tagdiffers from the value stored therein, it receives SIBs again andreplaces its currently stored values with the received SIBs.

FIG. 7 illustrates an example operation for eNB to notify altered systeminformation using SIB1 according to the present disclosure.

The eNB determines whether system information is updated in operation700. When the eNB ascertains that system information is updated inoperation 700, it increases the count of systemInfoValueTag value andthe count of systemInfoValueTagExt by one in operation 705.Alternatively, when the eNB increases the count of systemInfoValueTagvalue by one and then ascertains that wrap around occurs, it canincrease the count of systemInfoValueTagExt by one. The eNB includes theupdated IEs in SIB1 and broadcasts the SIB1 in operation 710.

Updating system information using a paging message and a value tag isperformed only when the down link channel between the UE and the eNB isin a favorable condition. When the down link channel between the UE andthe eNB has been in a condition impossible to perform the reception fora relatively long period of time, the UE cannot determine whether avalue tag of system information, received after restoring the down link,has been re-used. For example, when UE re-enters an area where it ispossible to receive service after it has been in an area where it isimpossible to receive service for a few hours, and re-acquires a valuetag, the re-acquired value tag can be identical to the value tag thatthe UE received before, and this result can suggest two possibilities.One is a case where the system information is maintained and thus thetwo value tags are identical to each other. The other is a case where,although the value tag that the UE had received is identical to thevalue tag that the UE re-receives, since wrap around occurs, systeminformation can actually differ.

In order to resolve these problems, the present disclosure defines avalidity timer for system information. When a specific event occurs, UEstarts the validity timer, or resets a validity timer that has beenoperating to the initial value and re-starts the validity timer. Whenthe time expires, the UE ascertains that the specific event does notoccur during the time interval specified by the timer, the UE determinesthat SI no longer is valid and acquires SI. Examples of the event arethe reception of SI by UE, the reception of a value tag identical tothat stored in UE, etc.

It is preferable that the validity timer has different values that varyaccording to DRX cycles of UE. UE which needs to minimize battery powerconsumption is set to have a relatively long DRX cycle. When UE whichneeds to minimize battery power consumption is set to have a relativelyshort time interval of validity timer, it can increase the ratio ofbattery power consumption to the overall battery power consumption whenre-acquiring system information (SI). On the other hand, when UE has arelatively short DRX cycle, it can consume a relatively small amount ofbattery power when re-acquiring system information (SI), compared withthe overall battery power consumption. Therefore, although the UE with arelatively short DRX cycle is set to have a relatively short timeinterval of validity timer, it does not cause any issues.

It is preferable that the validity timer has different values varyingaccording to lengths of valueTag. For example, the shorter the length ofvalueTag, the higher the probability that the valueTag is wrappedaround. Therefore, it is preferable that the time interval of a validitytimer is relatively small. In contrast, it can also be possible that thelonger the length of valueTag the larger the length of the validitytimer.

The present disclosure enables UE to properly employ the length of thevalidity timer, according to the length/type of a value tag, broadcastvia system information and the length of DRX cycle set to UE.

FIG. 8 is a flowchart that describes a method for UE to manage storedsystem information using system information and a valid period timeraccording to the present disclosure.

UE performs the cell re-selection in operation 805. The cellre-selection refers to the change in serving cells by UE. In particular,the cell re-selection means that, from among the cells allowing UE tocamp-on, including a current serving cell, UE camps on a cell satisfyinga specific condition such as a condition that it has the highest levelof down link signal intensity or the highest level of down link signalquality.

After performing the cell re-selection, UE acquires system informationfrom a new serving cell as follows in operation 810.

-   -   Reception of MIB in a frequency range corresponding to 6 PRB at        the system center frequency        -   Acquisition of SFN information, etc.    -   Acquisition of SIB1 via subframe 5 of a radio frame satisfying        SFN mod 8=0        -   PLMN ID, cell ID, Tracking Area Code, and the like.        -   systemInfoValueTag: a value between 0˜31. The maximum value            is 31.        -   systemInfoValueTagExt (optional)            -   Broadcast from only eNB supporting eDRX            -   independently have a meaning but can have a meaning                cooperating with systemInfoValueTag            -   In case of having a meaning independently,                -   The minimum value is 0. The maximum value is greater                    than that of the systemInfoValueTag (e.g., 255).                -   commonly applied to SI except for SI related to                    ETWS/CMAS or SFN, i.e., the remaining SI; even when                    any one of the remaining SI is altered, the count                    increases by one            -   In case of having a meaning, cooperating with                systemInfoValueTag                -   The minimum value is 0. The maximum value is an                    integer.                -   when systemInfoValueTag is wrapped around from the                    maximum value to 0, it increases by 1.        -   SchedulingInfo            -   Scheduling information regarding SIB 2˜SIB 17        -   receive and store the remaining SI, based on SchedulingInfo

UE stores the received SI as well as systemInfoValueTag andsystemInfoValueTagExt.

UE determines the time interval of the validity timer, considering acondition as to whether systemInfoValueTagExt is received and a DRXcycle in operation 815.

-   -   Method 1 considering a DRX cycle        -   When a cycle employed by UE belongs to a general DRX cycle,            i.e., when a cycle is less than or equal to 2.56 seconds or            T′ is not employed, the time interval of validity timer is            set to a first period.        -   When a cycle employed by UE belongs to an eDRX cycle, i.e.,            when a cycle is greater than or equal to 2.56 seconds or T′            is employed, the time interval of validity timer is set to a            second period.        -   The first and second periods are preset values. The second            period is greater than the first period.    -   Method 2 considering a DRX cycle        -   When a default eDRX cycle is not broadcast via system            information, the time interval of validity timer is set to a            first period.        -   When a default eDRX cycle is broadcast via system            information, the time interval of validity timer is set to a            second period.        -   The first and second periods are preset values. The second            period is greater than the first period.    -   Method considering systemInfoValueTagExt        -   When systemInfoValueTagExt is not broadcast via system            information, the time interval of validity timer is set to a            first period.        -   When systemInfoValueTagExt is broadcast via system            information, the time interval of validity timer is set to a            second period.        -   The first and second periods are preset values. The second            period is greater than the first period.    -   Method of using the maximum value of Value tag        -   When the maximum value of the Value tag is a first integer            (e.g., 31), i.e., when the maximum value of the Value tag is            the maximum value of the systemInfoValueTag, the length of a            validity time interval is set to the first period.        -   When the maximum value of the Value tag is a second integer            (e.g., 255), i.e., when the maximum value of the Value tag            is the maximum value of the systemInfoValueTagExt, the            length of a validity time interval is set to the second            period.        -   The first and second periods are preset values. The second            period is greater than the first period.

UE receives SI and then starts the validity timer. When the validitytimer reaches the validity time interval as determined above, UEdetermined that the validity timer has expired.

Each time that the validity of the currently stored SI is confirmed, UEresets the validity timer in operation to zero and then re-starts it inoperation 820. Confirming the validity of the currently stored SI refersto the following cases.

-   -   Validity confirmation by the reception of        SystemInformationBlockType1        -   In case of broadcasting only systemInfoValueTag, without            broadcasting systemInfoValueTagExt from a corresponding cell            -   When stored systemInfoValueTag is identical to received                systemInfoValueTag, the validity of the stored SI is                confirmed.        -   In case of broadcasting systemInfoValueTagExt and            systemInfoValueTag from a corresponding cell            -   A case that systemInfoValueTagExt has an independent                meaning                -   When store systemInfoValueTagExt is identical to                    received systemInfoValueTagExt, the validity of                    store SI is confirmed.            -   A case that systemInfoValueTagExt has an independent                meaning                -   When stored systemInfoValueTagExt is identical to                    received systemInfoValueTagExt, and stored                    systemInfoValueTag is identical to received                    systemInfoValueTag, the validity of store SI is                    confirmed.        -   The confirmation of System Information (SI) by the            re-reception of all SI            -   When stored systemInfoValueTagExt/systemInfoValueTag is                not identical to received                systemInfoValueTagExt/systemInfoValueTag, UE discards                the stored SI and newly receives SI.            -   UE considers that the validity of the newly received SI                has been confirmed.

When a preset period of time has elapsed after the validity of stored SIwas confirmed, UE considers that the stored SI no longer is not valid.In this case, UE discards the stored SI and then newly re-acquires SI inoperation 825. The preset period of time is the validity time intervaldetermined in operation 815, i.e., a first period or a second period.When UE moves to a new cell or the alteration of related systeminformation (e.g., a condition as to whether systemInfoValueTagExt istransmitted or a condition as to whether an eDRX cycle is transmitted)does not occur, the UE continues employing the selected validity timeinterval.

The method and apparatus according to embodiments of the presentdisclosure is capable of efficiently managing system information, usinga valid period timer, in discontinuous reception mode, in a mobilecommunication system.

Although the present disclosure has been described with an exemplaryembodiment, various changes and modifications can be suggested to oneskilled in the art. It is intended that the present disclosure encompasssuch changes and modifications as fall within the scope of the appendedclaims.

What is claimed is:
 1. A method by a terminal in a wirelesscommunication system, the method comprising: receiving systeminformation from a base station; identifying whether validity timeinformation is included in the system information; determining avalidity time as a first time when the validity time information isincluded in the system information; determining a validity time as asecond time different from the first time when the validity timeinformation is not included in the system information; and determiningthe system information is valid or not based on the determined validitytime.
 2. The method of claim 1, further comprising: when the validitytime information is included in the system information, selecting afirst timer applying the first time.
 3. The method of claim 1, furthercomprising: when the validity time information is not included in thesystem information, selecting a second timer applying the second time.4. The method of claim 1, further comprising: identifying a validity ofthe system information by checking a system information value tag(systemInfoValueTag) included in the system information; and if thevalidity of the system information is identified, resetting andre-starting a timer.
 5. The method of claim 4, further comprising: usingthe system information between a first time point when the validity ofthe system information is identified and a second time point after thedetermined validity time has elapsed from the first time point, and notusing the system information after the second time point.
 6. The methodof claim 1, further comprising: discarding the system information if thesystem information is determined to be expired by operating a timerapplying the determined validity time; and receiving, if the systeminformation is discarded, new system information from the base station.7. A method by a base station in a wireless communication system, themethod comprising: determining whether validity time information isincluded in system information to determine a validity time of thesystem information, wherein the validity time is determined as a firsttime when the validity time information is included in the systeminformation and the validity time is determined as a second timedifferent from the first time when the validity time information is notincluded in the system information; and transmitting the systeminformation to a terminal so that the terminal determines the systeminformation is valid or not based on the determined validity time. 8.The method of claim 7, wherein a first timer applying the first time isselected when the validity time information is included in the systeminformation.
 9. The method of claim 7, wherein a second timer applyingthe second time is selected when the validity time information is notincluded in the system information.
 10. The method of claim 7, whereinthe system information comprises: a system information value tag(systemInfoValueTag) for identifying a validity of the systeminformation.
 11. The method of claim 10, further comprising: wherein thesystem information is used in the terminal between a first time pointwhen the validity of the system information is identified and a secondtime point after the determined validity time has elapsed from the firsttime point, and wherein the system information is not used in theterminal after the second time point.
 12. A terminal in a wirelesscommunication system, the terminal comprising: a transceiver; and acontroller coupled with the transceiver and configured to control to:receive system information from a base station, identify whethervalidity time information is included in the system information,determine a validity time as a first time when the validity timeinformation is included in the system information, determine a validitytime as a second time different from the first time when the validitytime information is not included in the system information, anddetermine the system information is valid or not based on the determinedvalidity time.
 13. The terminal of claim 12, wherein the controller isconfigured to: when the validity time information is included in thesystem information, select a first timer applying the first time; andwhen the validity time information is not included in the systeminformation, select a second timer applying the second time.
 14. Theterminal of claim 12, wherein the controller is configured to: identifya validity of the system information by checking a system informationvalue tag (systemInfoValueTag) included in the system information; andreset and re-start a timer if the validity of the system information isidentified.
 15. The terminal of claim 14, wherein the controller isconfigured to: use the system information between a first time pointwhen the validity of the system information is identified and a secondtime point after the determined validity time has elapsed from the firsttime point; and not use the system information after the second timepoint.
 16. The terminal of claim 12, wherein the controller isconfigured to discard the system information if the system informationis determined to be expired by operating a timer applying the determinedvalidity time, and receive, if the system information is discarded, newsystem information from the base station.
 17. A base station in awireless communication system, the base station comprising: atransceiver; and a controller coupled with the transceiver andconfigured to control to: determine whether validity time information isincluded in system information to determine a validity time, wherein thevalidity time is determined as a first time when the validity timeinformation is included in the system information and the validity timeis determined as a second time different from the first time when thevalidity time information is not included in the system information, andtransmit the system information to a terminal so that the terminaldetermines the system information is valid or not based on thedetermined validity time.
 18. The base station of claim 17, wherein afirst timer applying the first time is selected when the validity timeinformation is included in the system information, and wherein a secondtimer applying the second time is selected when the validity timeinformation is not included in the system information.
 19. The basestation of claim 17, wherein the system information comprises: a systeminformation value tag (systemInfoValueTag) for identifying a validity ofthe system information.
 20. The base station of claim 19, wherein: thesystem information is used in the terminal between a first time pointwhen the validity of the system information is identified and a secondtime point after the determined validity time has elapsed from the firsttime point; and the system information is not used in the terminal afterthe second time point.